PoC: Add built-in CCF contract with encode function #3638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
turbolent
changed the title
turbolent
force-pushed
the
bastian/ccf
branch
from
5ea3f3b
to
1d2d5b3
Compare
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit 85f46f7 Collapsed results for better readability
|
|
Unfortunately there's currently a cyclic import between |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work towards #3637
Description
Add a new built-in contract
CCF, which allows encoding an exportable value to .The parameter of
encodeis a reference, so it can accept both structs and resources, and supports move-semantics of resources (i.e. does not consume the passed resource-kinded value)For now this is a PoC showing how this could be done.
TODO
masterbranchFiles changedin the Github PR explorer